This issue is driving me nuts. I've done everything I can to whittle things down to as simple a state as possible. I have only one thread making calls into KM_Controller, and that thread runs on a 100mSec timer interrupt using a System.Windows.Forms.Timer, so it is synchronous to my application main thread. The timer interrupt handler first verifies that the board is connected and fully initialized, then makes a call to UpdateMainStatus(). MainStatus is used for most of the dispolay update data, with additional calls to various functions in KM_Controller, and Interpreter.
My app ALWAYS seems to work fine, but if I have KMotion open when my app exits, I get an exception from KMotion (unable to write memory exception). If I do a Dispose on the KM_Controller as my app is exiting, then I get the exception in KM_Controller.Dispose. If I don't do a Dispose, my apps seems to exit OK, but crashes KMotion after it's closed. I can't see anything I'm doing wrong, yet the failure is absolutely consistent. Something is causing KMotion to disconnect when my app exits, but I can't for the life of me figure out what's causing it.
Regards,
Ray L.
--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Brad,
>
> I thought for a while yesterday I had rid myself of the crash on exit, but it's back. It's originating in the call to Interpreter.Dispose within KM_Controller.Dispose, and the specific exception is:
>
> "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
>
> This occurs any time I exit my app. Is there something I'm not doing that I should be? I've tried calling Dispose from the FormClosing and FormClosed events, and get the same exception either way.
>
> Regards,
> Ray L.
>
